I'm also experiencing this problem after upgrading to Ubuntu 19.10. I'm
using xserver-xorg-video-amdgpu 19.0.1-1ubuntu1 so either it's not
completely fixed, or I'm experiencing a different but very similar
issue.
One of the linked bug reports suggested the crash occurs in the XFCE
compositor. I
It sounds like the dmic is connected to PCH instead of codec.
please generate a log under windows10 by this tool.
thx.
** Attachment added: "RtHDDump_V236.zip"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+attachment/5306138/+files/RtHDDump_V236.zip
--
You received
uname -a
Linux lilian-dev 5.0.0-37-generic #41+redmiv2 SMP Mon Nov 18 05:09:35 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
1. installed as the order below:
789 sudo dpkg -i linux-headers-5.0.0-37_5.0.0-37.41+redmiv2_all.deb
790 sudo dpkg -i
** Attachment added:
"pactl_list_before_switching_output_device_back_and_forth.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306132/+files/pactl_list_before_switching_output_device_back_and_forth.log
--
You received this bug notification because you are
I ran the following steps:
1. Power laptop on with bluetooth turned off
2. Turn BT on in gnome settings and set my BT headphones in pairing mode
3. Pair the headphones.
4. In Sound settings, it looks like the selected device is the BT headphones,
but if I play something it outputs on the laptop
Yes, the internal microphone works perfectly fine in Windows 10 and is
being detected as Intel Smart Sound
--
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/1852922
Title:
Internal
** Attachment added:
"pactl_list_after_switching_output_device_back_and_forth.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306133/+files/pactl_list_after_switching_output_device_back_and_forth.log
--
You received this bug notification because you are a
@GrzesiekC, can you check for apparmor denials when running thunderbird?
I.e. have a terminal running "journalctl -f | grep DEN", and share the
output here.
Do you have an apparmor profile being enforced for thunderbird? I.e.
what is the output of:
sudo apparmor_status | grep thunderbird
--
please test the v2 kernel, at least you could see a front mic as
internal mic from UI.
https://people.canonical.com/~hwang4/redmi/v2/
make sure the kernel is redmiv2 by checking with uname -a
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is
1) external mic not plugin
:~$ sudo hdajacksensetest -a
[sudo] password for lilian:
Pin 0x12 (Not connected): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Black Mic, Left side): present = Yes
Pin
1. installed as the order below:
sudo dpkg -i linux-image-xxx.deb
sudo dpkg -i linux-modules-.deb
sudo dpkg -i linux-modules-extra-xxx.deb
2. restart and boot to the test kernel.
3. Open settings and find Input tag from Sound.
- The internal mic was not visible
3. insert the external mic
-
Can also confirm the issue is fixed with the -proposed package
--
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/1847551
Title:
Mutter 3.34.1 broke Night Light, screen color profiles in
[Expired for ibus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ibus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Please install and test this kernel, at least you could see the internal
mic, and maybe the internal mic can work.
https://people.canonical.com/~hwang4/redmi/v1/
And please also test the external mic.
If they don't work as expected, please collect an alsa-info.txt with
coeff enabled.
sudo su
My new machine (one week old) is receiving these as well:
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ journalctl | grep "operation=\"open\"
profile=\"snap.gnome-system-monitor.gnome" | wc -l
77549
which half the log!
$ journalctl | wc -l
144263
--
You
Has the internal mic ever worked before? or on other OS like windows or
other linux distributions?
--
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/1852922
Title:
Internal
First of all, TB 68.2.1 with gData 68.2.1 installed from
https://addons.thunderbird.net/en-GB/thunderbird/addon/provider-for-
google-calendar/ should work. The workaround is described in comment
#22.
--
You received this bug notification because you are a member of Desktop
Packages, which is
(In reply to llh from comment #71)
> (In reply to paul from comment #23)
> > I tested the workaround with gData for Calendar and it worked as expected.
>
> Confirmed! /Lars
What is this workaround you mention? I'm still stuck
--
You received this bug notification because you are a member of
I took a screenshot of typing switching to dash search box as reported
in comment #46. Typing froze, and what I typed was put into the dash
search box as seen below. It was supposed to be in the browser where I
was typing it.
** Attachment added: "keyboard freeze.png"
** Bug watch added: Red Hat Bugzilla #1740610
https://bugzilla.redhat.com/show_bug.cgi?id=1740610
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=1740610
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Update: the issue at GNOME repository was re-classified from nautilus-
related to glib-related: https://gitlab.gnome.org/GNOME/glib/issues/1942
.
** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #1942
https://gitlab.gnome.org/GNOME/glib/issues/1942
--
You received this bug notification
I can actually only get this to manifest *for files created by
Nautilus*. Files that are created from an ssh session or by cd-ing into
the /run/user/1000/... directory are unaffected. So I guess this also
affects Nautilus?
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status:
This is an interaction between vim and GVFS, so I've added GVFS as
affected.
** Also affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- vim-gtk can no longer save to GVFS STFP mounts in 18.04
+ vim-gtk can no longer save to GVFS SFTP mounts in 18.04
--
Public bug reported:
I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13.
Everything works just fine except the microphone which is not being
detected at all.
My alsa-info output: http://alsa-
project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2
System info:
Description:
Thanks for pointing that out because I also had
__GL_SYNC_DISPLAY_DEVICE=DP-0 in /etc/environment as completely forgot
to mention that in my previous comment to yours here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: "Screenshot of a message that requires extra
authentication."
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852844/+attachment/5306087/+files/Screenshot%20from%202019-11-15%2022-01-33-1.png
--
You received this bug notification because you are a member of
Thank you Sebatien for looking into that.
The GNOME bug is filed as
https://gitlab.gnome.org/GNOME/nautilus/issues/1293 .
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1293
https://gitlab.gnome.org/GNOME/nautilus/issues/1293
--
You received this bug notification because you
Just had a look at my own settings: I have "Dim display when idle"
unchecked in the AC power tab, checked in the Battery tab. I am still
getting a dark screen every now and then, even though I mostly work on
AC power.
--
You received this bug notification because you are a member of Desktop
@Maik Schulze did that change anything? are you still getting the error?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749
Title:
Intermittent black screen on HP EliteBook 840 G1
Additionnal note for the previous comment: it also works when Sync to
VBlank is enabled (tested with glxgears), but causes tearing for the 60
hz monitor.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in
Hello,
In my case, appending __GL_SYNC_DISPLAY_DEVICE=DP-0 in the
/etc/environment file (DP-0 is my 144hz monitor - see X Server XVideo
Settings in NVIDIA X Server Settings) seems to works (config: GTX
1070/60 Hz + 144 Hz monitors).
I forced resolution + frequency in NVIDIA X Server Settings for
Public bug reported:
The action to take when the battery is critical can only be one of the
following:
# Possible values are:
# PowerOff
# Hibernate
# HybridSleep
Adding Suspend to that list makes perfect sense. My laptop is currently
powering off on low power which is useless as I'll be losing
** Changed in: gnome-calendar
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1756901
Title:
GNOME Calendar crashes in remove_source when
Black internal screen on my G1 820 too. May be its a problem with
function "lower screen intensity when inactive" (energy), i have
disabled it now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1847896 ***
https://bugs.launchpad.net/bugs/1847896
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This particular bug has already been reported and is a duplicate of bug
1847896, so it is being marked as such. Please
Public bug reported:
Hi,
When I'm boot my computer and the Gnome Shell login screen appears, if I
try to reboot the computer from the menu available in the top right, the
button does nothing.
I tried clicking multiple times, my computer won't reboot.
However, If i'm logged into my desktop, and
I too have the same problem with my Dell Inspiron 1525. I doubt it's the
extension Dash to Panel that's getting kicked out.
--
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/1849055
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/issues #264
https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264
** Also affects: gnome-calendar via
https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264
Importance: Unknown
Status: Unknown
--
You received this
I have the same problem with Asus K54HR, rfkill says that phy0 is hard blocked.
I tried to reinstall Ubuntu 19.04 and 19.10, reset the bios, with no solution.
WiFi works well on Windows 10.
I am happy to provide any additional information to solve the issue.
--
You received this bug
In this attachment it can be seen that Minimized Nautilus File Manager
is unminimized and unresponsive after Gnome Shell refresh/reload.
Also Nautlilus become responsive when I click to open Nautilus File
Manager.
** Attachment added: "After Gnome-Shell refresh/reload, Minimized Nautilus File
Public bug reported:
Let's say you have minimized one or more applications such as Firefox,
Gnome Tweaks or even Nautilus File Manager. These applications will be
become unminimized after gnome-shell restart and become unresponsive,
unless I press to minimize/maximize them, they won't be
Correction: When I said "Alt+F2" above, I meant "Ctrl+Alt+F1", as the
whole X had frozen.
I should also mention that I'm running a Radeon RX 5700 GPU with the
default AMDGPU driver - and am separately experiencing random GPU
lockups, which could explain the whole-screen lockup I mentioned in
Public bug reported:
When hitting the delete key on an item on the desktop, a beep is
emitted, and nothing happens. When launching a separate Nautilus window,
navigating to ~/Desktop, and trying to delete items from this folder,
the Nautilus window freezes. At this point, no new Nautilus windows
44 matches
Mail list logo
