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, pr
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 any
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 the
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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded packages, which i
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bug
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 w
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 Ubuntu
Touch seeded packages, which is subscribed to polic
Public bug reported:
I've written an issue here:
https://github.com/stuartlangridge/ColourPicker/issues/63
Pick (a color picker distributed as a snap) will not launch. The creator
of the application believes this to be a problem with my system, not
with their app. Apparently, AppArmor is preventi
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.
```
[
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 regressi
** 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 in
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
workaround
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 i
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 Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges i
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.
Altho
*** This bug is a duplicate of bug 1795135 ***
https://bugs.launchpad.net/bugs/1795135
** This bug has been marked a duplicate of bug 1795135
XFCE window buttons are not clickable at the top of the screen
--
You received this bug notification because you are a member of Ubuntu
Touch seede
No change in Disco. Still missing the entry at
"com.ubuntu.desktop.pkla".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375
Title:
Desktop unabl
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 Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375
Tit
20 matches
Mail list logo
