Public bug reported:
I just upgraded a working system from an up-to-date 18.04.5 installation
to 20.04.1 and lost sound in the process.
The upgrade itself was uneventful but now Pulseaudio lists the dreaded
dummy output as the only available sound card.
Alsa correctly sees the card as Card: HDA
Adding output of alsa-info
** Attachment added: "alsa-info.txt.cecwOZNY4C"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912933/+attachment/5456223/+files/alsa-info.txt.cecwOZNY4C
--
You received this bug notification because you are a member of Desktop
Packages, which is subscr
** Summary changed:
- Pulseaudio dummy output after upgrade to 20.04
+ [Asus P8B75-M/VIA VT1708S] Pulseaudio dummy output after upgrade to 20.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad
Confirmed F10 issue with gnome-terminal. Can't really use htop settings
as F10 is bound to terminal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1380194
Title:
Terminal emula
terminal edit->preferences->general (uncheck) enable the menu accelerator key
(F10 by default)
This solve the issue
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1380194
Title:
I made it public but still no one looking at it
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1908866
Title:
548.2 KB file is giving infinite size text file output while exractin
@jowfdoijdfdwfwdf yes, you can disalbe this annoing "feature".
But how many people want to use F1/F10 keys in terminal? A lot of
applications like mc, htop use these keys.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in
Public bug reported:
[Policy]
AutoEnable=true
not working
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
Uname: Linux 5.10.0-051000-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDm
Problem happened again.
Here enclosed, you will find the result of a journalctl for last boot
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912472/+attachment/5456315/+files/prevboot.txt
--
You received this bug notification because you are a memb
Please see comment #20.
My online backup set specifically excludes $HOME/.cache (the default or
unset value of $XDG_CACHE_HOME) to avoid churning backup snapshots with
transient application cache data.
I don't know if chromium ever respected $XDG_CACHE_HOME (it would appear
from the bug report me
@~malakai1197
You're out of luck really, switch distributions that don't use half-
baked snaps. Maintainers think that this usability regression is an
"opinion" and that tells really more than enough.
--
You received this bug notification because you are a member of Desktop
Packages, which is su
As far as I can tell at the moment this bug appears to have been fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1872504
Title:
date modified is wrong for files on an exfat
Thanks for your work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1891739
Title:
4. and 5. mouse-button on thumb does not react during save-dialogue in
LO
Status in libreoff
Public bug reported:
Ubuntu 21.04: Start simple-scan, click on 'scan' I have a message 'Failed to
scan - Unable to connect scanner'
debug log says 'SANE_STATUS_NO_MEM'
Same scanner works fine on Ubuntu 20.10
corrado@corrado-x6-hh-0122:~$ simple-scan --debug
[+0,00s] DEBUG: simple-scan.vala:2012:
Public bug reported:
To reproduce this bug, I click the power icon in the activity bar in the
top right of the screen and select Power Off/Logout > Suspend. The
computer will suspend. I can unsuspend within a few minutes without
error.
If I close my clamshell and leave the laptop suspended for mo
I have also been getting this error as soon as my system updated from
Kernel 5.4.0-58-generic x86_64 bits to Kernel 5.8.0-38-generic x86_64
bits.
Booting from the 5.8 kernel stops with a black screen and a blinking
cursor. Pressing the PC power off switch performs a power off.
Rebooting with the
Same problem, same DAC/amp. I'm using kernel 5.8.0. It worked yesterday
morning before I took my laptop out of the dock for the day, but hasn't
worked since. The Schiit Fulla has jacks for both mic and headphone; the
mic seems fine (though I can't select it, I can see the input level in
pavucontrol
Public bug reported:
Description:Ubuntu 20.04.1 LTS
Release:20.04
I am submitting a patch for /usr/share/grub/grub-mkconfig_lib to fix the
usage of GRUB_FLAVOUR_ORDER in method version_test_gt().
I have installed the XanMod-LTS kernel in my Ubuntu 20.04 installation.
The Ubuntu 20.04
Public bug reported:
This is the same issue as originally reported in bug 1765363 but that
report is old and has a lot of extra data on it so it was requested that
a new bug be opened if we were still having the issue.
So... I am still having the issue, at least with the 390 series drivers
(my la
Fixed upstream in 1.20.7-8 (?)
** Changed in: gpm (Ubuntu)
Importance: Undecided => Medium
** Changed in: gpm (Ubuntu)
Status: New => Triaged
** Changed in: gpm (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: gpm (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xt
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1904583
Title:
SRU: Backport the latest developments on drivers detecti
*** This bug is a duplicate of bug 1885675 ***
https://bugs.launchpad.net/bugs/1885675
Thanks. This looks like the same problem as bug 1885675 so let's use
that...
** Also affects: avogadro (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Segfault in iris_dri.so
+
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: avogadro (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/188567
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1885675
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mpv (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1885675
Ti
** Summary changed:
- mpv crashed with SIGSEGV in stream_state from ... from iris_blorp_exec from
blorp_clear from clear_color from iris_clear
+ Apps crash with SIGSEGV in stream_state from ... from iris_blorp_exec from
blorp_clear from clear_color from iris_clear
** Also affects: avogadro (Ubu
** Summary changed:
- external headset microphone not working on Ubuntu 20.10 (not even wired,
cable headset)
+ [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu
20.10 (not even wired, cable headset)
--
You received this bug notification because you are a member of De
** Tags added: groovy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1911369
Title:
[radeon] Horizontal lines of screen corruption after last update.
Status in linux package in Ubuntu:
*** This bug is a duplicate of bug 1905519 ***
https://bugs.launchpad.net/bugs/1905519
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 1905519, so it is being marked as such. Please look
In case the freeze is actually some part of the shell or display server
crashing, please also follow these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Desktop
Packages,
Thanks. I can't see a problem in that log... Next time a freeze happens,
please try waiting for 10 seconds, the reboot and again run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
--
You received this bug notification because you are a member of Desktop
Packages, whi
*** This bug is a duplicate of bug 1846718 ***
https://bugs.launchpad.net/bugs/1846718
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 1846718, so it is being marked as such. Please look
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 try:
sudo apt install xserver-xorg-video-openchrome
and then reboot.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Summary changed:
- El monitor de la pc funciona a una resolución muy baja
+ [viafb] VIA Chrome 9 HC stuck at 640x480
** Tags added: viafb
** Changed in:
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/19128
*** This bug is a duplicate of bug 1912833 ***
https://bugs.launchpad.net/bugs/1912833
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.36.4-1ubuntu1~20.04.2, the probl
*** This bug is a duplicate of bug 1912833 ***
https://bugs.launchpad.net/bugs/1912833
** This bug has been marked a duplicate of bug 1912833
Gnome shell crashes when using wl-copy or wl-paste
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
Thanks for the bug report. I reproduced the crash on 20.04 and it led
to:
https://errors.ubuntu.com/bucket/?id=/usr/bin/gnome-
shell%3A8%3Awl_shell_surface_role_configure%3Ameta_window_wayland_configure%3Ag_closure_invoke%3Asignal_emit_unlocked_R%3Ag_signal_emit_valist
--
You received this bug n
Which is:
https://errors.ubuntu.com/problem/6de6e7a931b1ab1175f233d776feb5a3fa74a04b
** Description changed:
+ https://errors.ubuntu.com/problem/6de6e7a931b1ab1175f233d776feb5a3fa74a04b
+
+ ---
+
This has worked before, but with the latest update of mutter on
14.01.2021 the gnome-shell cras
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubu
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bu
The crash doesn't seem to occur on 21.04, just giving an assertion
failure warning:
surface_state_changed: assertion
'wl_window->has_last_sent_configuration' failed
So it seems the issue was fixed in 3.38 via:
https://gitlab.gnome.org/jadahl/mutter/-/commit/29776c99a85c071c48336e04b6e8e7191b2b
@butterfly was trying to install the package but it says, unable to
locate package.
This is what i tried,
Imported the ppa,
`sudo add-apt-repository ppa:kelebek333/nvidia-legacy`
`sudo apt update`
and tried,
`sudo apt install nvidia-graphics-drivers-340` but it says unable to locate
package.
This bug was fixed in the package gpm - 1.20.7-8
---
gpm (1.20.7-8) unstable; urgency=high
* Fix enabling of gpm under systemd by adding #DEBHELPER# marker to
gpm.postinst. Try not to break other init systems while doing so.
(Closes: #980726, LP: #1912575)
-- Axel Beckert
Four problems with that :(
* PPAs are not supported.
* This bug is closed.
* You should use bug 1910709 for 20.04.
* Bug 1910709 is also closed.
If the fix provided for 20.04 in bug 1910709 does not work for you then
please open a new bug by running:
ubuntu-bug nvidia-graphics-drivers-340
I don't think having packages from both Nvidia-340 and Nvidia-460
installed at the same time is supported. Please uninstall or purge the
packages from whichever version you don't need.
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: New => Invalid
--
You received this bug noti
Please check for crashes using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
But regardless of the outcome there, this is probably an Nvidia driver
bug.
** Summary changed:
- Xorg freezes after suspend
+ [nvidia] Xorg freezes afte
Thanks for the bug report. Please check:
1. If 'timidity' is installed then uninstall it (bug 1793640)
2. If 'pipewire' is installed then see bug 1897965.
3. If you are not sure about 1 and 2 then run:
dpkg -l > packages.txt
and attach the resulting text file here.
4. If you have a 'pul
Thanks for the bug report. A few thoughts:
1. xserver-xorg-video-intel is old and not supported. Please uninstall
it to make sure you're using the newer default driver ('modesetting').
2. Your kernel log shows constant hardware errors from the 'Intel
Corporation 8 Series PCI Express Root Port 3':
Thanks for the bug report. It looks like you have the overlay key set to
'Super_R'. That means the left Super key won't work and many keyboards
don't even have a Super_R. Please try this:
gsettings set org.gnome.mutter overlay-key Super_L
** Changed in: gnome-shell (Ubuntu)
Status: New =
Thanks for the bug report.
It appears you don't have a working kernel driver for your Nvidia GPU,
and that maybe an unsupported driver was installed manually.
If you have any way of logging in then please use the 'Additional
Drivers' app to install a supported Nvidia driver on the system.
If you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libreoffice (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/b
Please explain in more detail what problem you are/were experiencing.
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1741365
What kind of problem do you encounter when trying to reinstall Ubuntu?
Does it still happen?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
54 matches
Mail list logo
