*** This bug is a duplicate of bug 2004021 ***
https://bugs.launchpad.net/bugs/2004021
** This bug has been marked a duplicate of bug 2004021
Moving video position /scrubbing in Totem (Videos) causes video to freeze
(but not audio)
--
You received this bug notification because you are a
This is fixed in Ubuntu Lunar (23.04). After upgrading, I can no longer
reproduce.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2017027
Title:
Sound device missing
This shows what I see when I try to switch between audio output devices.
** Attachment added: "Screenshot of the Sound settings"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2017027/+attachment/5665297/+files/Screenshot%20from%202023-04-19%2015-30-46.png
--
You received this
Public bug reported:
GNOME isn't exposing the monitor audio device. It doesn't show up as an
option to switch to in the Sound settings.
This is the device, from 'lspci':
> 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23
> HDMI/DP Audio Controller
It's an LG ultrawide
It may be due to vsync being always enabled:
https://www.phoronix.com/news/Wayland-Tearing-Control-Proto
--
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/1997597
Title:
Wayland
Public bug reported:
This is a regression that came with the change from Xorg to Wayland.
It's particularly bad for playing fast-paced games, such as first-person
shooters. The pointer tracking has a small but significant delay, which
cannot be reproduced on the Xorg session.
Similar reports:
-
Public bug reported:
So you just installed Ubuntu 22.04 and you try to play an mp4 video.
Totem will complain about missing an H.264 decoder, as you can see in
the command line output:
Missing plugin: gstreamer|1.0|totem|decodificador H.264 (Main
Profile)|decoder-video/x-h264, level=(string)3,
Most of them were .mp4 videos downloaded from Tik Tok with yt-dlp
(https://github.com/yt-dlp/yt-dlp) or by right-clicking and using the
'Save as' dialog.
Here's one example:
https://v16-webapp.tiktok.com/150af96e4903dde52283b7197631cd1e/62a10462/video/tos/useast2a/tos-
No, I can reproduce it with many different video files. Nothing shows up
on the cmdline. Firefox plays the videos just fine, by the way.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
1. I ran "totem filename.mp4" and reproduced the problem, but nothing is
logged to the console.
2. The package gstreamer1.0-vaapi is not installed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
Public bug reported:
The video stops playing at a certain random frame, like it's been
paused. You can drag the range control and move forwards and backwards
and the frame will change as expected, but toggling play/pause does
nothing.
I can only reproduce this on Ubuntu 22.04. On Debian 11 it
*** This bug is a duplicate of bug 1872268 ***
https://bugs.launchpad.net/bugs/1872268
Thanks, it's a duplicate then. I'm attaching the video again, let's see
if it works now.
** Attachment removed: "Reproducing the bug in video"
** Attachment added: "Reproducing the bug in video"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+attachment/5531404/+files/Grava%C3%A7%C3%A3o%20de%20tela%20de%2007-10-2021%2023%3A08%3A21.webm
--
You received this bug notification because you are a member of Desktop
Public bug reported:
# Steps to reproduce:
1. Press "Super + A" to see all apps.
2. Find an app launcher group (many launchers grouped in one item) and open it
3. Close the group
# What happens:
The pagination indicators become duplicated, followed by glitchy animations.
This can be temporarily
Public bug reported:
Enabling the screen reader in GNOME and using it with any browser leads
to occasional glitches and crashes.
Firefox, for example, crashed and asked me to file a crash report to Mozilla.
GNOME Web just restarted itself out of nowhere, same as Chromium.
The arrow up/down
So, I've questions about this bug if it comes from firefox, or mutter,
or wayland because every time I try use Firefox 88 the Wayland session
freezes and nothing else works besides Magic Key to restart my machine.
--
You received this bug notification because you are a member of Desktop
Hi there!
This report page doesn't have any from reported version but it does have
the report from the previous version, version 87:
https://crash-stats.mozilla.org/report/index/09389e82-1bfb-43fe-
bd10-2b8940210408
--
You received this bug notification because you are a member of Desktop
Public bug reported:
After updating firefox deb to version 88, every time I play YouTube
videos, some times in several tabs, then Wayland crashes and the system
freezes. For try workaround this crash, I've to use the magic key SysRq
(Alt + SysReq) with "REISUB" characters to safely reboot my
Probably related to bug 1872796 too
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1922241
Title:
[Wayland] Dash to dock don't show all applications
Status
Public bug reported:
This extension has been updated these days and the "All" button (next to
"Frequent" button) has crash and no longer shows all applications.
Disabling Ubuntu-Dock via Extensions Panel this function works perfectly
again.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
I'm attaching the requested logs.
Near the end of this file you'll see the last action I performed, which
was the CTRL+ALT+PRINT+REISUB combination to reboot. You'll also see
that there is a long crash log related to AMDGPU.
Oh, and this time when it crashed I attempted to switch TTY, and then
I can't see any files in /var/crash/, even after applying the workaround
and reproducing the freeze again.
This time the freeze was more severe. There was no response from the
keyboard and a hard reset was the only way to recover.
--
You received this bug notification because you are a member
Public bug reported:
Automatic suspension causes the system to freeze on resume. This doesn't
happen if I suspend it manually by opening the system menu and pressing
the suspend button. Suspension works flawlessly when it is triggered
manually.
When the system resumes from automatic suspension,
Correction:
It's not about where the cursor is placed when the animation ends, it's
about whether the cursor is moving or not.
Keep the cursor still, as I said previously, and the bug doesn't happen.
Keep the cursor moving while the sliding animation is running, and the
problem is nearly always
An observation about how to reproduce this bug:
As soon as you click the "Show Applications" button on the dock, move
your mouse to the target position of any of the icons before the sliding
animation is over. This will usually trigger the glitch.
Keeping the cursor still after you click that
Update: this is also reproducible on Wayland.
--
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/1876532
Title:
Badly positioned icons in the app grid
Status in gnome-shell package
Here's the gif showing a strange animation happening right after the app
grid is opened, which causes a displacement of the icons.
** Attachment added: "Animation showing how to reproduce the problem"
** Attachment added: "Screenshot of the first part of the grid"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+attachment/5365468/+files/Captura%20de%20tela%20de%202020-05-02%2019-47-31.png
--
You received this bug notification because you are a member of Desktop
Public bug reported:
This bug is best explained with images. I've attached two screenshots
showing what the app grid looks like right after it's opened. A gif has
also been recorded to show a glitch in the animation as the icons slide
in.
This is not reproducible in Fedora 32 with GNOME 3.36 on
I forgot to tell you that I never see any dialog when I plug the
earphone. It's a feature of some desktop environments, right? I have
never seen it in Xfce.
The capture source changes to "headphone" every time I plug the
earphone, and when that happens, there is no sound output. Changing it
to
Oh, I can finally hear sound through the earphones by changing the
capture source. Too bad the change doesn't persist after I remove and
reinsert the connector. Every time that happens, I must change it to
Headset Mic, otherwise there will be no sound output.
It also works when I do it through
I have attached a screenshot of that screen, because I couldn't find any
Capture Source or Input Source there. Maybe it has a different name or
is missing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
** Attachment added: "screenshot alsamixer capture"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+attachment/5361512/+files/Captura%20de%20tela_2020-04-27_06-51-37.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
Running amixer sset 'Capture Source' 'Internal Mic' returns error:
amixer: Unable to find simple control 'Capture Source',0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875249
Public bug reported:
Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no
sound output when you plug an earphone/headset. The built-in speakers,
on the other hand, are working properly. This is a laptop, Dell Inspiron
11 3162.
I checked volume levels with alsamixer, I played
This bug was fixed in Xubuntu 19.04, if I remember correctly. But on
later releases it became reproducible again.
I'm currently running Xubuntu 20.04, and most of the widgets on the top
panel are affected, with the exception of Whisker menu icon (sometimes),
the task switcher and the Notes widget
I think I can't reproduce this anymore on Xubuntu 20.04. I left the
laptop idle and after 30 minutes it was suspended as expected, without
making any fixes (clean install).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
You mean I should try an older version? Then I think I should try v5.0.x
first. As you can see, it takes time to reproduce it again. I don't know
how to intentionally reproduce it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The logs I attached previously only refer to the session AFTER the
system restarted. So I've collected the logs from the previous boot this
time, which will contain the relevant information.
I'm attaching the output of: `journalctl -b-1`
** Attachment added: "output of journalctl -b-1"
Apparently, the logs I collected are from after the reboot, so they're
probably not relevant. How do I collect logs from before the reboot?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
I was able to reproduce it again. The system quickly became
unresponsive, so I had to reboot with the REISUB combination. After the
system started again I collected the logs. I wasn't using Nautilus of
the image viewer this time.
** Attachment added: "journalctl -b0 after the freeze"
Public bug reported:
When you have 3 or more windows open, the overview will overflow
vertically. A piece of the bottom row is cut off from the screen. See
the screenshot, please.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
I have been trying to reproduce it in the last days, but I couldn't. I
managed to get nearly 100% use of swap space again, while simultaneously
using Nautilus and Eye of GNOME (which is what I was doing at the exact
moment the freezes began), but it didn't happen again. Nothing changed
about my
Here's the new issue:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2164
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164
--
You received this bug notification because you are a member of Desktop
Packages, which
I'll create the new issue there.
I have only one monitor.
--
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/1849135
Title:
Clicking Activities in the corner doesn't work
Status in
I can reproduce this problem with a USB stick as well. I suggest
changing the title to "Removable media icon stays on the dock after
eject".
To reproduce, I've inserted my USB stick used to install Ubuntu,
automounting it; Two items appeared, one that says "Ubuntu 19.10..." and
another saying
Public bug reported:
It starts with very subtle stuttering that you notice when moving
windows around, then keeps getting worse and worse until it starts
freezing the UI for many seconds. I could only reproduce it twice in a
couple of days.
The applications open at the time are usually Atom,
Let me add that I also tested a GNOME session (package 'gnome-session')
and there was no difference from the results of testing the Ubuntu Xorg
session. The proposed package does NOT fix the issue for me.
--
You received this bug notification because you are a member of Desktop
Packages, which
I have tested 'mutter' version 3.34.3-1ubuntu1~19.10.1 from eoan-
proposed on an Xorg session, and it doesn't fix the issue. Testing was
made after package installation, followed by a system reboot.
mutter/eoan-proposed,now 3.34.3-1ubuntu1~19.10.1 amd64 [installed]
I don't know what other
Public bug reported:
Please read this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1645553
I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
messages are still being spammed into my Xorg logs.
```
[
It was already reported.
Here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
And here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1601
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1649
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
** Bug watch
Public bug reported:
According to this page:
https://wiki.ubuntu.com/Sound#Primary_sound_output, "if you manually
choose an output device in the “Sound” settings panel or a similar
utility, that choice should be followed". Well, despite me having
explicitly selected the headset as the output
No extensions were installed. Also, I'm using the native AMDGPU drivers,
not the proprietary ones.
I've tested the vanilla GNOME session as you suggested, and the bug is
there too. Due to the hover highlighting of the panel items, I had a
visual cue to test with. The highlighting does not happen
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
-
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
+
** Attachment added: "Journalctl logs"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+attachment/5298947/+files/journalctl.txt
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is.
Public bug reported:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
Specs:
- Graphics:
Public bug reported:
I close the laptop lid and let it suspend. On resume, the whole desktop
is frozen for a while. Nothing works during this time, no CAPS LOCK
indicator LED, neither TTY switching. Then the screen goes dark and I
see the LightDM login screen. I was logged out.
This is a
** Description changed:
- On 16.04 (XFCE session and others) and possibly later the power-manager
- is unable to suspend the system when the user is inactive. A PK user-
- agent dialog is presented for the user to authenticate first - and as
- this action occurs specifically when the user is idle
I can also reproduce this on both of my computers running Xubuntu 19.04,
a desktop and a laptop.
Just to be extra clear on what the issue is:
If the computer is left idle for 10 minutes, the screen locks. When 15
minutes have passed, it should suspend, but it never does. I unlock the
screen to
Thanks for the response. Sorry for the delay, I didn't get a
notification about this.
If by admin you mean one that has sudo privileges or a member of group
`adm`, then yes. It's the default user created by the installer.
I could reproduce this on Arch Linux and other distros IIRC. The
Public bug reported:
I've configured it so that the system would suspend after pressing the
power button. This does not happen.
How is it reproducible?
It started after updating from Ubuntu 18.04.2 to 18.04.3. New packages, new
kernel, new bug. On Ubuntu 19.04, this has been reproducible since
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+attachment/5280446/+files/dmesg.txt
** Description changed:
In the Power tab, the option "When the power button is pressed" is set
to "Suspend". However, this action is not
** Attachment added: "journalctl output"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+attachment/5280445/+files/journalctl.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in
Public bug reported:
In the Power tab, the option "When the power button is pressed" is set
to "Suspend". However, this action is not executed on power button
press. It does nothing.
This is always reproducible on Ubuntu 19.04, while on Ubuntu 18.04.2 it
works as expected.
gnome-control-center
The solution is right here, so simple to apply. Why is this ignored? No
one else suspends their machines? Merge the necessary polkit rule,
please.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-desktop-privileges in Ubuntu.
Sorry, I'm not sure what to remove. My file is slightly different from
the one in that commit. Is it OK to comment out everything at /usr/bin
/start-pulseaudio-x11? There are other if blocks that don't seem to be
related.
I will try to comment out only the if block that references `bell.ogg`
and
All right, that fixes it. Now I have the expected behavior. Only one
sound plays: the one selected through GNOME Settings.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Public bug reported:
One is the alert sound chosen through GNOME's sound settings, the other
seems to be the default alert from the sound theme, which we can't
change without using dconf-editor.
When an alert sound is triggered, both sounds play at the same time
instead of one.
Things I've
Public bug reported:
With CSD enabled, Firefox 66.0.4 displays white corners at the top-left
and top-right of the window.
Ubuntu version: 19.04 (fully updated)
Version: Firefox 66.0.4 (64-bits)
Desktop Environment: GNOME 3.32.1 (default)
GTK theme: Yaru (default)
GPU: Radeon RX 560 Series
Public bug reported:
Description: When session is locked either using dm-tool or light-
locker, lightdm greeter is functional (you can type your password and
press Enter to unlock the session) but screen is not turned on, and
remains turned off even when you move the mouse or press any key.
No change in Disco. Still missing the entry at
"com.ubuntu.desktop.pkla".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-desktop-privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375
Title:
Desktop unable to Suspend
Your workaround worked for me too. I'm running Xubuntu 18.04. Now I can
suspend the machine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-desktop-privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375
Title:
73 matches
Mail list logo