Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Public bug reported:
I just installed Ubuntu 20.04.
but sometimes, the screen is freezing. This is very very bothering me.
Please help me.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-gene
Upload to H and SRU to G
** Changed in: wslu (Ubuntu Groovy)
Importance: Undecided => Low
** Changed in: wslu (Ubuntu Hirsute)
Importance: Undecided => Low
** Changed in: wslu (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: wslu (Ubuntu Hirsute)
Status: New => Fi
The bug is not yet actionable, because a decision was not achieved yet.
The team working on 2020H2 bookmarks improvements wanted to complete
collecting users feedback and telemetry before evaluating further steps.
Thus, while I'm in favor of this change, we should at least wait the end
of that proj
Further testing. Using the KMS driver results in mesa defaulting to
llvmpipe software rendering making YouTube a painful experience.
So the fkms is needed for 3d acceleration but glitchy graphics... ho-
hum.
On Thu, 14 Jan 2021, 16:34 David Mohammed, wrote:
> Do note.
>
> If I change in /boot/
Also affected. Having Ubuntu 20.04 LTS (the default flavor).
lspci -v (yes, I have 2 gpus)
04:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller
(rev a1)
Subsystem: NVIDIA Corporation TU116 High Definition Audio Controller
Flags: bus master, fast devsel,
Public bug reported:
Hi everyone :)
It's a problem that occurs without any possible correlation with other
event (wake up, sleep etc).
In the middle of a session the Wi-Fi simply stop working and not only
the system doesn't reconnect automatically, but you need to turn off and
back on the Wi-Fi
Mattia Rizzolo writes:
> Could you please describe:
>
> * Which release you are basing this bug on?
Buster
> * Describe why you'd want the static library?
My mistake, I had gotten confused while trying to fix a broken build
with a libxslt dependency and thought I needed it. You can close this
** Changed in: libxslt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxslt in Ubuntu.
https://bugs.launchpad.net/bugs/1908500
Title:
libxslt.a missing from libxslt1-dev
Status in libxs
** Changed in: thunderbird (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1907470
Title:
Thunderbird latest/stable snap's rel
Public bug reported:
* Impact
That's the current GNOME stable update, including some fixes and translation
updates
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-38/NEWS
* Test case
The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
This affected me too - it broke the Ubuntu version of Virtualbox.
--
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/1911614
Title:
Ubuntu 20.04 and 20.04.1 images use linux-generic-h
Found another crash the same way in bug 1911921
--
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/1864052
Title:
gnome-shell crashed with SIGABRT in
src/core/window.c:1591:meta_window_u
*** This bug is a duplicate of bug 1908429 ***
https://bugs.launchpad.net/bugs/1908429
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
I experienced the same issue but it dissappeared after i purged my xorg
installation and reinstalled it from root shell(ctrl+alt+F4). i think main
issue was with libinput in my case.
just thought to provide this information
--
You received this bug notification because you are a member of Deskt
but it reappeared after some time
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/362359
Title:
Focus gets stuck to a window - impossible to select other windows
Status in xorg-se
** Changed in: gnome-control-center (Ubuntu Groovy)
Status: Incomplete => Fix Committed
** Changed in: gnome-control-center (Ubuntu Groovy)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-con
Evince also stops while trying to print in Ubuntu 21.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1809685
Title:
The evince application often freezes
Status in Evince:
New
Stat
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evince (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/180092
In 21.04 the printmenu from evince stops the whole programm and can only
be killed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1800925
Title:
can't print pdf files with evince, pri
The issue is fixed now in thunderbird 78.6.1 (but it requires the core18
snap from the candidate channel)
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => Fix Committed
** Bug watch added: Mozilla Bugzilla #1680527
https://bugzilla.mozilla.org/show_bug.cgi?id=1680527
** Also af
The relevant syscall is `sched_setaffinity`, which when used with a
first argument of `0` is allowed in the default policy. Can someone who
is experiencing this bug run an strace to determine what argument
chromium is trying to use with sched_setaffinity ? We allow any
sched_setaffinity arguments w
Public bug reported:
* Impact
That's the current GNOME stable update, including some translation updates
https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-38/NEWS
* Test case
The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
Check that a GNO
Full stack trace, seems retracing failed. Oh well.
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911921/+attachment/5453545/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/ubuntu/+source/
Only tested on hirsute, no idea if it happens on groovy or focal too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1911921
Title:
gnome-shell crashed with SIGABRT in
src/core/
Does anyone know if an update of the libx11 package for lubuntu 18.04
will be released?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion `!xcb_xlib_threads_seque
@therealsujitk @ubuntu-iremonger
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1910709
Title:
DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
For the record, I talked to Robie who is on the SRU team, and he said:
« IMHO, I think that breaking the other packages to bump Thunderbird is
inevitable. Technically I don't think that's within the remit of the SRU
team - it's a TB thing. I think we should figure out how to mitigate as
much as p
Hello Hui, or anyone else affected,
Accepted pulseaudio into groovy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.2-1ubuntu2.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Hui, or anyone else affected,
Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.10 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hi Guys,
I am facing the same issue. My laptop is T440p. The touchpad does not
work after the login screen.
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ Microsoft Microsoft Nano Tr
Public bug reported:
mmm
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Archit
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1910709
Title:
Do you have clean sound from HDMI1, if Linux PC is used? Today I
discovered it is garbled, need to know if it is my or everyone problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs
This bug was fixed in the package gnome-control-center -
1:3.38.3-1ubuntu1
---
gnome-control-center (1:3.38.3-1ubuntu1) hirsute; urgency=medium
* New upstream version based on Debian (lp: #1911918)
* debian/patches/0016-diagnostics-Add-Whoopsie-support.patch:
- display the who
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
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/b
A transition of pepperflashplugin-nonfree to a dummy package will happen
via bug #1911463. Debian will keep the dummy in Bullseye, and drop it
from the archive only in bookworm. Probably it's preferable also for us
to wait with removing it until after the 21.04 release.
--
You received this bug n
1.8.5 has landed in hirsute now, so marking hirsute as fixed released.
** Changed in: flatpak (Ubuntu Hirsute)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flatpak in Ubuntu.
https://bugs.lau
Launchpad has imported 23 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1680527.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://h
I added the packaging tag because this was a packaging error in the
20.04 and 20.04.1 images.
** Tags added: packaging
** Description changed:
+ Beginning about January 8th Focal users that installed Focal using
+ either the Ubuntu 20.04 or 20.04.1 installation media began getting
+ updated to t
I updated the bug description to better explain why I believe this is a
bug, but I left the original content below the break.
** Description changed:
Beginning about January 8th Focal users that installed Focal using
either the Ubuntu 20.04 or 20.04.1 installation media began getting
update
I filed bug #1912032 concerning the failure of nvidia drivers to install
during a fresh installation of Ubuntu 20.04.1 because when download
updates is selected it auto-updates to a 5.8 series kernel during
installation.
--
You received this bug notification because you are a member of Desktop
Pa
Eventually I was able to install 5.4.0-62-generic and the stick is now working.
However I'm still seeing updates of 5.8 line with apt update/apt upgrade.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bu
This bug was fixed in the package gnome-desktop3 - 3.38.3-1ubuntu1
---
gnome-desktop3 (3.38.3-1ubuntu1) hirsute; urgency=medium
* Merge with Debian. Remaining changes (lp: #1911934)
- Add 04_compute_average_color.patch: Compute the avergage color in
gnome-desktop itself, n
I installed the focal-proposed updates yesterday, just checked and I can
confirm the background corruption issue is still there, tho it's not as
much as before. Before it used to change to a complete grey static, but
now the wallpaper is still visible to an extent. I'll attach a
screenshot.
** Att
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]
** Changed in: libreoffice (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bu
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.ne
[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-extension-ubuntu-dock
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
[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
[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
[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
Public bug reported:
I installed CUPS on Ubuntu based OS (Raspbian) but it does not work with
HP Laser MFP 135a
apparently it needs ULD drivers. I'm not familiar with CUPS or Printer
drivers for that matter so I'm not sure why CUPS does not work with IPP-
over-USB printers out of the box
lsusb -
The bug's still present, but the fix in #7 works for me too.
"as workaround editing /etc/gdm3/custom.conf to uncomment
`WaylandEnable=false` should fix this"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.
same issues happened on my ASUS Zephyrus M. i think it's alc294's problem.
as Ian Choy (iancmx) mentioned, 0x21 set as headphone that laptop could detect
the headphone when you plug in, but no sound comes from headphone
ubunutu 20.04lts
--
You received this bug notification because you
The bug persists with accented characters if the dead key is the first
character you type. I mean, open the overview, type "á" and you see just
"a". Then type another "á" and it shows correctly. Same if you type
"lá", the accent shows correctly because the dead key wasn't the first
thing you typed.
57 matches
Mail list logo