Here often gnome software cannot update Gitkraken snap, it shows an
error message that Gitkraken uses classic confinement.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1876879
I removed ~/.config/pulse just now, and seems fixed, but i have to test
a few more to be sure. But it was happening mostly when plug hdmi, so
device output was changed to hdmi, and i couldn't just change back to
internal. Then i try to select hdmi 5.1 or 7.1 profile, and as in video
attached, this
I was wrong,i don't fixed completely. Just now I connected a bluetooth
phone and happened again, the sound was not playing in internal or
bluetooth anymore.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Hi!
I fixed before your post with the command "dconf reset -f /org/gnome/".
I guess the gnome extension "Sound Input & Output Device Chooser" may have done
something wrong, but i'm not sure, and just disable or uninstall didn't solve
the problem, what solved was the command "dconf reset -f
hi! I'm here again because some package upgrade, or something else (i
dont't know what) just fixed it. Now I can connect with just one click.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
I have been using Ubuntu 20.04 since it was released. Suddenly, a few
days ago, the sound device output selection (gnome-control-center >
Sound > Output device) stopped work properly. It is starting as HDMI by
default (it used to be "internal" before the bug, but this is not
About the Philips SHB3075, i had tested just for music. I had borrow
that, so, i didn't do more tests. What is the handsfree service? The
volume control in that phone worked independent, regardless, from volume
in the system.
--
You received this bug notification because you are a member of
** Attachment added: "Same bug in Dell inspiron 5480 laptop."
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5387956/+files/dell_bad.cap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in
Hi! I had test the same redmi airdots in more scenarios, that led me to
guess that, while autoconnection is not a bug, manual connection is
really an Ubuntu bug, since it worked fine in Linux Mint 19.3 in the
same hardware.
These was the new tested cenarios (all these with redmi airdots phone):
*
autoconnection works.
Besides the auto-connection bug is just with redmi+ubuntu, manual connections
(and disconnections) are also useful if you use the same headphone in more than
one device.
** Attachment added: "autoconnection after turn phone on"
I tested a third headphone, Philips SHB3075, in my acer laptop, and
autoconnection works, but manual reconnections not. For manual
connections is the same than for redmi, i had to try connect a lot of
times than it works.
** Attachment added: "Philips SHB3075 cap, manual connection bad"
** Attachment added: "btmon cap from lenovo bug"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5378974/+files/lenovo.cap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
well, i had done both tests (redmi in other laptop and same laptop with
another phone), and the result was quite confusing. Seems the bug occurs
with the combination of ubuntu+redmi
1 - Testing Redmi In an old laptop Lenovo G470, autoconnection (after turn
phone on again) not works at all (just
bluetoothctl connect is the same that connecting in ubuntu settings?
I tried to connect via terminal, and I had same problem:
*TURN PHONE ON*
bluetoothctl connect 1C:52:16:B6:64:01
Attempting to connect to 1C:52:16:B6:64:01
Failed to connect: org.bluez.Error.Failed
Trying a lot of times, after
Hi, i just found out that if i try to click *a lot* of times in
connection button i can connect the second time.
the only message in log was not really in the same time when i tried to
connect or disconnect
D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC0 is accessible: no
D:
Hi! i'm sorry for taking so long to reply, i lost the email notification
in spam.
Well, I did that. There is a log of log messages there, but nothing when
i tried to connect again (i was checking with tail -f).
** Attachment added: "a.txt"
Hi, thanks for help. When i manually try to connect in ubuntu settings,
yes, there are this messages:
May 20 12:50:29 felipe-Nitro-AN515-52 bluetoothd[1257]: Unable to get Headset
Voice gateway SDP record: Device or resource busy
May 20 12:50:29 felipe-Nitro-AN515-52 bluetoothd[1257]: connect
Hi, I'm sorry, I couldn't do that, because soon after i had reported, i
upgraded distro to 20.04, and then this doesn't happens anymore.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
Public bug reported:
Steps:
1 - Enable automatic login and the option to turn off screen after X minutes,
in gnome settings.
2 - Reboot
3 - DON'T type password when its asked for unlock default-keyring, just wait
the time to auto lock screen (x minutes).
4 - move mouse or type keyboard. It
Public bug reported:
Besides after each login the gnome-software works fine, after some condition
(seems me that it happens after suspend, and keep suspended for some hours) the
search does not works anymore, it keeps in an infinite loading. Also, the
images in initial page doesn't load.
When
Public bug reported:
- Open 2 or more windows of the same program, as expected, they will be
agrouped in the same icon in panel
- With one of that, put in a non-maximized small size window, righ click on its
title bar, and enable Always on top
- open a windows of another program and maximize
21 matches
Mail list logo
