There is one important step for reproducing this bug, not only in
gnome-terminal, but also in nautilus and gedit:
* open multiple tabs
* !!! reorder one of the tabs !!!
* leave pointer hovering over one of the tabs
* observe tooltip appearing, and cursor changing to reflect loss of focus in
the
Thank you for following up.
I have managed to complete a commit bisect of the Ubuntu kernels and can
confirm that the first bad commit is
851cc40f47677174527a1decbd1074feacd15a93:
ALSA: hda: call runtime_allow() for all hda controllers
BugLink: https://bugs.launchpad.net/bugs/1876765
Last known working kernel: 5.4.0-33, next installable Ubuntu kernel
5.4.0-37 introduces the bug.
I have tested that saving "options snd_hda_intel power_save=0" to a file
under /etc/modprobe.d and rebooting to a kernel from -37 onwards is a
valid workaround.
Lines mentioning ALSA from
http://chang
Ignore my last comment about last known working kernel, I've rebooted to
5.4.0.40 and I still see this issue, will try and do more testing on
kernel versions to see if I can find where it changes, and will also
look into the power_save options.
--
You received this bug notification because you ar
The output of cat /proc/asound/card1/codec#0 after running alsa-info
differs slightly to that included within the alsa-info log itself (in
#8):
26c335
< Converter: stream=0, channel=0
---
> Converter: stream=5, channel=0
38c347
< Converter: stream=0, channel=0
---
> Converter: stream=5, ch
To add to #9, as well as the headphones being detected after running
alsa-info, I can confirm that they still work as expected after
detection.
As this may be a bug introduced by a kernel change, the current kernel
running is 5.4.0.42.45 (generic, x86_64), whereas the previous one I was
running wh
Then after the fresh boot, I connected the headphones, verified no
sound, then re-ran alsa-info which gave the following attached log.
** Attachment added: "alsa-info log with headphones plugged in"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+attachment/5396230/+files/a
After running alsa-info, it appears that the headphones were detected
and started to show in Settings GUI, also showing in the attached pacmd
list report.
** Attachment added: "pacmd list after alsa-info with headphones connected"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888
For reference, after a fresh boot without headphones plugged in on my
machine, the alsa-info command gives the attached output.
** Attachment added: "alsa-info log fresh boot with no headphones connected"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+attachment/5396229/+f
For comparison, a log from before I plug in the headphones (after a
fresh boot)
** Attachment added: "pacmd list after a fresh boot"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+attachment/5396218/+files/pacmd_list_fresh_boot.log
--
You received this bug notification b
And a log from after I use pavucontrol to manually enable the 17h audio
controller while the headphones are plugged in, and confirming that they
do work as they used to.
** Attachment added: "pacmd list after manual switch"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+at
As requested - after a fresh boot, and plugging in headphones and
verifying that there is no sound from them.
** Attachment added: "pacmd list after plugging in headphones"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+attachment/5396217/+files/pacmd_list_headphone_plugge
Public bug reported:
I boot my system without any sound devices plugged into any jacks;
checking Gnome settings Sound, Output Device is "Dummy Output" (no other
options available in drop-down list). I plug in headphones into the
front jack and play some audio, but do not hear any sound from the
he
Re: comment #14: I never said GParted wasn't working - I said that in my
case running GParted was causing Disks (gnome-disk-utility) to show
buggy behaviour.
>From reading the udisks2 issue, the problem seems to do with the udev
change event that's triggered either by running GParted or making
par
I've tested with 18.04 and the newer udisks also shows the same
behaviour.
>From further digging I've found that there is an open issue for a udisks
partition property loss bug which seems to be an exact match at
https://github.com/storaged-project/udisks/issues/425
** Bug watch added: github.co
I see a similar problem with incorrect partition information in gnome-
disk-utility. I am not sure if it's exactly the same as the OP's issue
as in my case the problem is solely triggered by running GParted, and
not by the deletion/modification of partitions as mentioned by the OP.
I suspect that
Interesting that the last person mentioned Caja - there is potential
progress in narrowing down where the problem lies in their issue tracker
(https://github.com/mate-desktop/caja/issues/528).
Nautilus, Caja and Nemo all exhibit this same behaviour. In the Caja
issue tracker zaps666 suggested that
Still a problem in 16.04 LTS - constantly burning 20% CPU on idle.
--
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/207135
Title:
pulseaudio uses too much CPU
Status in pulseaudio p
I found that disabling AMD C1E support in BIOS mitigates this issue (and
also another problem I had with boot stalling without mouse/keyboard
input) - this bug may be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1012806.
The Phenom II X3 710 supports C1E power saving state,
Public bug reported:
Audio playback via ALSA (snd_intel_hda) & pulseaudio inevitably 'skips'
(repeats buffer content) intermittently a few times each hour, and
severely whenever the screen is blanked for inactivity.
CPU load is low (mostly idle).
I didn't have this problem with my previous fresh
OK - I'll chalk this one up to the timer issue I mentioned.
Taking out "nolapic_timer" from grub options has allowed pulseaudio to
detect and use high precision timers and it has performed much better
(lower CPU usage, concurrent streams OK) - I still get the occasional
audio glitch, but I'll deal
Verbose log from pulseaudio
** Attachment added: "Output of pulseaudio -"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1533783/+attachment/4549431/+files/pulseaudio_debug.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
Public bug reported:
While playing a youtube video, starting up another audio playback (in
this case, in Rhythmbox) causes the video player to crash.
I expected the video (with its audio track) to continue playback without
crashing, while Rhythmbox gets mixed in as a second, concurrent audio
sour
Perhaps upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=378605
would solve this?
** Bug watch added: GNOME Bug Tracker #378605
https://bugzilla.gnome.org/show_bug.cgi?id=378605
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to g
24 matches
Mail list logo
