This reference was removed when GNOME Software was adopted.
** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/765333
Titl
Public bug reported:
Package info:
Package: miniupnpd
Version: 2.1-6.1
Priority: optional
Section: universe/net
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Thomas Goirand
My system info:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Code
Public bug reported:
After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over usb-c
(Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working properly.
Revert to 5.8.0-63 resolves the problem.
The problem is independent of nvdia-drivers (tried 470, 460 and intel only
** Package changed: ubiquity (Ubuntu) => ubuntu-translations
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922447
Title:
Wellcome to Ubuntu Mate slideshow is not entirely in Spanish
To manage noti
Public bug reported:
It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking
at first i watch video then put it on full screen (especially in browser
chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete"
or try "Ctrl+alt+F2" to text mode.
then I sea
** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298069
Title:
On the internet slide During 14.04 install it use
Public bug reported:
nvidia graphic problem
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon
[Expired for libwebp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libwebp (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/191997
[Expired for codeblocks (Ubuntu) because there has been no activity for
60 days.]
** Changed in: codeblocks (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.n
[Expired for mysql-8.0 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-8.0 (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/19
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1928950
T
[Expired for openjdk-lts (Ubuntu) because there has been no activity for
60 days.]
** Changed in: openjdk-lts (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/bug
[Expired for update-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: update-manager (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.n
[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: 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/1931196
Title:
no
To m
Yes, this impacts me as well. I was using VirtualBox at the time. It may
be unrelated, by computer has been freezing/crashing regularly since I
bought it 9 months ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
*** This bug is a duplicate of bug 1938978 ***
https://bugs.launchpad.net/bugs/1938978
** This bug has been marked a duplicate of bug 1938978
nvidia-340 kernel module failed to build (ERROR: Kernel configuration is
invalid)
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1938978 ***
https://bugs.launchpad.net/bugs/1938978
** This bug has been marked a duplicate of bug 1938978
nvidia-340 kernel module failed to build (ERROR: Kernel configuration is
invalid)
--
You received this bug notification because you are a member
Further to my previous comment #21 above, I have found a workaround to
get the shared folders working again with the latest image. It appears
that the problem is with the virtualbox-guest-utils package included in
the image.
Here are the steps that I performed in order to get a virtualbox
ubuntu/f
To avoid to have many packages to be removed you need to downgrade all
the 9.3 packages.
~
First find them.
dpkg -l | grep 2.31-0ubuntu9.3
ii libc-bin 2.31-0ubuntu9.3 amd64 GNU C Library: Binaries
ii libc-dev-bin 2.31-0ubuntu9.3 amd64 GNU C Library: Development binaries
ii libc6:amd64 2
To avoid to have many packages to be removed you need to downgrade all
the 9.3 packages.
~
First find them.
nikau@nikubuntu:~$ dpkg -l | grep 2.31-0ubuntu9.3
ii libc-bin 2.31-0ubuntu9.3
amd64GNU C Library: Binaries
ii
** Changed in: oem-priority
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/1835660
Title:
initramfs unpacking failed
To manage notifications about this bug go to:
One more thing, per my test, on LAN, you can kind of reproduce this
issue by
On iperf server:
1. set packet delay to 5ms
"tc qdisc add dev eno1 root netem delay 5ms" or
"tc qdisc change dev eno1 root netem delay 5ms"
2. run iperf3 server by command "iperf3 -s"
On Client (say the machine
Yes, I know. I did had posted the issue there first :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938650
Title:
iwd on Ubuntu 20.04 stopped working since update to kernel 5.11
To manage notifi
Hi Sebastian,
Sorry to hear it's not working on your side. That means the current
direction currently been working on does not really solve the issue
happens in your combination.
Here is what you can try:
1. upload sosreport log. like run `sudo sosreport`, and upload the output file
in /tmp.
2.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: scribus (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/1939213
Title:
sc
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
/etc/default/ufw has:
DEFAULT_OUTPUT_POLICY="ACCEPT"
This means that all outgoing traffic is allowed. If you would like to
change that, you can use:
$ sudo ufw deny outgoing
This will make it more difficult for you to manage the firewall since
you'll have to add rules like:
$ sudo ufw allow ou
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
I am also having the same "Invalid argument" error with 'ubuntu/focal64'
version '20210803.0.0' when doing vagrant up.
Manually running the mount command from inside the guest machine brings the
same error.
The host machine (also Ubuntu focal64) is running vagrant 2.2.18 and Virtualbox
6.1.22
I
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Rebuilt scribus (in impish PPA), but it didn't make a difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939213
Title:
scribus 1.5.7+dfsg-1build1 segfaults on impish
To manage notifications
Public bug reported:
trying to install kmymoney in terminal with sudo apt install kmymoney,
than it crashes and a messagebox is shown for reporting the problem
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: kmymoney-common (not installed)
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Public bug reported:
impish with updated packages. I find this entry in /var/log/syslog:
Aug 8 00:22:28 gunnar-ubuntu-dev kernel: [ 2710.184084] scribus[16001]:
segfault at 0 ip 7f526c9e5c74 sp 7ffe750286d0 error 4 in
libQt5Core.so.5.15.2[7f526c923000+30f000]
But scribus 1.5.7+dfsg-1 ru
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. B
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (
** Changed in: linux-signed (Ubuntu)
Assignee: (unassigned) => Xavier (xavier69)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881757
Title:
webcam is detected but not working with kernel 5.4.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: erlang (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/1917492
Title:
pac
Public bug reported:
Hello!
After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I
have noticed some screen flickering. I had the same problem previously
on Fedora after upgrading to the 5.0 series kernel, but this was not
present on Ubuntu 20.04 on either the 5.4 or 5.8 series k
It seems this bug has resurfaced? I'm running duplicity 0.8.19 on Ubuntu
20.04.
If I have the file tree:
test
- root
- ...
- other stuff
And run
duplicity --exclude **/root --exclude-if-present .nobakup test
file:///.../backup
duplicity prints a non-fatal error:
Error accessing possibl
I compiled the new images that you sent. Linux 5.10.56- and received
the same error about Libc6 being downlevel, but when I rebooted that kernel it
booted with what appeared to be the same errors as 5.13.7.
Boot.log shows:
[FAILED] Failed to start Load/Save Screen Backlight Brightness of
That failed when I rebooted:
Error:/boot/vmlunz-5.13.7-051307-generic has invalid signature
Error: you need to load the kernel first
Press any key to continue
Pressing a key takes me back to the Grub screen and I can select 5.11.0-25 to
reboot the system
I don't think I did anything wrong, but I
There are three possible causes
- firmware bug
- kernel bug
- user error (read-only variables), though why does that give I/O rather than
ENOSPACE
I'm going to reassign this one to linux for a check on the kernel side,
but I suspect it's a firmware issue.
** Package changed: shim-signed (Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (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/1938163
Title:
Please fix this. We cannot install Ubuntu 21.04 clean.
It's impossible for regular user.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938163
Title:
package shim-signed 1.50+15.4-0ubuntu7 failed to
Public bug reported:
Ubuntu 20.04.2 LTS
I ran into a problem recently
(https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due
to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11
where the userspace tools don't match the zfs-kmod version. After the
update the system
I asked in the zfs github issue and the answer is that the versions must
match. It might be an incompatibility between zfs-0.8.3-1ubuntu12.12 and
zfs-kmod-2.0.2-1ubuntu5 though not sure how easy it is to deal with this
when using HWE.
--
You received this bug notification because you are a member
Yeah good point, not sure whether the userspace tools version needs to
match the kmod version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939177
Title:
Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs se
Public bug reported:
When installing xubuntu 20.04 it fails at the end of the installation
during grub-install it seems wrong source file location and target
device has been used.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~2
This does not seem to occur in 20.10.7-0ubuntu1~20.04.1 anymore.
** Changed in: docker.io (Ubuntu)
Status: Confirmed => 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/1925303
Title
I've also seen this. I wondered if the problem is that the libraries and
utilities haven't been updated. I doubt that it's intended for a version
0.8.3 ZFS send and receive to run on a ZFS 2.0.2. kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
Hello,
I hope this is the proper place to report this bug.
I am using the daily built and I see that some strings are not translated but
they are not available on Launchpad for translation.
Also, I noticed that the language packs are not updated every 2 weeks
like I read so
>Is it possible to add to this list a package that isn't in the Ubuntu
repositories e.g. Brave Browser?
No. The Ubuntu project will never support or depend on third party
packages. If you want to use Ubuntu in a way that is supported and
install updates and upgrades without issues then you will ha
hui wang : Bug #1939205
help plz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850
Title:
Dell XPS 17 (9710) PCI/internal sound card not detected
To manage notifications about this bug go to:
Public bug reported:
no more sound device /output since dist upgrade from 20.10 to 21.04
tried both official ubuntu kernel 5.11.0.26 and newer
5.13.8-051308-generic
alsa log:
http://alsa-project.org/db/?f=07dfaad1d5d30948449dc36f0caaf39c99145cce
lsb_release -rd
Description:Ubuntu 21.04
Rel
Please provide more information.
Which desktop? Which release?
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
FWIW I'm using it with sanoid/syncoid
(https://github.com/jimsalterjrs/sanoid) which enables -s by default if
supported by the zfs version.
syncoid has a --no-resume option that might work (but have yet to try).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I updated Ubuntu 20.04.2 LTS by the normal update process to
5.11.0-25-generic and sound is finally working on Dell XPS 9700.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912673
Title:
sounds not
Thanks for the reply srdjan.
As this bug report and all of its duplicates refer to Ubuntu 16.04,
which is no longer supported, I'll close this as "Invalid". It may well
have been fixed in that release but it's not worth the trouble to
ascertain whether it was or not.
** Changed in: hundredpapercu
Appears that the -s option does not work. Can you double check if the
recv works when not using the -s option?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939177
Title:
Ubuntu 20.04.2 LTS kernel
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this issue some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported now that
Ubuntu 20.04 is no longer
Google translates reply as:
Good Morning!
My problem when updating my notebook with Linux version 16.04, with a lot of
regret that I did it, I can't handle with the old times, the shortcuts are all
different, the mouse command is just bad to work, it just happens that it gives
command when it s
Public bug reported:
Muy Buenas en información de software mas controladores, no aparece nada
sin embargo nvidia x lo puse como por demanda es decir intel en segundo
lugar y baje la resolución de pantalla a 1080x 748 ayuda donde estan
los controladores? gracias
ProblemType: Bug
DistroRelease: U
** Changed in: ubuntu
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/1871333
Title:
Errors were encountered while processing: linux-firmware linux-
image-generic
Public bug reported:
I'm using ubuntu focal 20.04.
the problem is with zfs header sources in ubuntu in /usr/include/libzfs/.
in zfs source code there is a header file:
"zfs/lib/libzfs/libzfs_impl.h" and there are includes to other .h files:
#include
#include
#include
#include -> * problemati
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
I'm setting this bug to "Incomplete" as it's not seen any activity for
some time. If this is still an issue when using a currently maint
These three packages are no longer included in any currently released
version of Ubuntu so closing.
** Changed in: oxide-qt (Ubuntu)
Status: New => Invalid
** Changed in: webapps-applications (Ubuntu)
Status: New => Invalid
** Changed in: webbrowser-app (Ubuntu)
Status: New
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
software-center is no longer included in Ubuntu.
** Changed in: ubuntu-gnome
Status: New => Invalid
** Changed in: software-center (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a memb
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
User no longer uses Launchpad so cannot ask if still an issue
with a later Ubuntu release. Closing as "Invalid".
** Changed in: ubuntu-gnome
Status: New => Invalid
--
You received this bug notification because you are a member of U
software-center no longer part of Ubuntu so closing.
** Changed in: software-center (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510661
Title:
Unable to Tur
Further to comment #2, closing 'Ubuntu GNOME' task
** Changed in: ubuntu-gnome
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590726
Title:
Nautilus Locations colour i
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
User no longer uses Launchpad so cannot ask if issue is still
apparent in a current Ubuntu release. There are no similar
outstanding bugs reported by other users.
Closing as "Invalid".
** Changed in: ubuntu-gnome
Status: New => I
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
$ ps -Af | grep -v grep | egrep -w "PPID|$(pgrep -u $USER systemd)"
UID PIDPPID C STIME
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
$ ps -Af | grep -v grep | egrep -w "PPID|$(pgrep -u $USER systemd)"
UID PIDPPID C STIME
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
- $ loginctl list-sessions
- SESSION UID USER SEAT TTY
- 99 1001 sebastien seat0
- 79 12
** Package changed: chromium (Ubuntu) => chromium-browser (Ubuntu)
** Summary changed:
- no abre chromiun en linux mint 20
+ no abre chromiun en linux mint 20 (Chromium doesn't open in LM 20)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Package changed: ubuntu => linux (Ubuntu)
** Tags removed: groovy ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913198
Title:
mouse acceleration does not work on Logitech G402 Mouse
To
** Description changed:
Hi,
After each logout from KDE, I can find the `systemd --user` process when
I log into a tty{2..6} console and its remaining 23 children still
running :
$ loginctl list-sessions
SESSION UID USER SEAT TTY
52 1001 sebastien seat0
79 12
1 - 100 of 159 matches
Mail list logo
