Thanks. That is very helpful.
** Summary changed:
- [HP Laptop 14-ma0xxx] No sound after suspend
+ [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty,
but not 5.0.1)
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
--
You received this bug notification
Please install this dkms, reboot and redo the test.
If the headset-mic still doesn't work, please enable dump_coeff and
generate an alsa-info.txt.
thanks.
** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb"
Indeed my conclusion was wrong because I mixed up the versions. The bug
does affect some newer versions although it seems that it was solved in
the meantime before reappearing again.
To correct, I observed the following:
* The bug does NOT affect kernel version 4.18.0-15 (Tested using a Live
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
It sounds like you made a typo there. The points you list suggest the
regression started between kernels 5.0.1 and 5.1.5:
* The bug does not affect kernel version 5.0.1-050001 (Tested on my install of
19.04 with a manually installed kernel)
* The bug does affect newly build kernel version
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
I was now able to try a few different versions leading to the following results:
* The bug does not affect kernel version 4.18.0-15 (Tested using a Live install
of 18.04.2)
* The bug does not affect kernel version 4.20.17-042017 (Tested on my install
of 19.04 with a manually installed kernel)
*
Before I get a chance to look into this later today, I'd like to note
that the network device is not firewalling those packets since a few
days ago before I installed 18.04 on this machine it was behaving as
expected and the 16.04 machine mentioned in the OP is not being blocked
(it is on a
** Summary changed:
- [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all
+ [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at
all
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Please:
1. Reproduce the problem again.
2. Use your workaround to recover. Do not reboot.
3. Run this command:
journalctl -b0 > journal.txt
4. Send us the file 'journal.txt'.
** Tags added: nouveau
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Do not see
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1830489
Title:
I don't Know
Status in Ubuntu:
Incomplete
Bug description:
Please try to take a video of the problem and attach it here. A video is
important because it tells us what type of "flickering" we are dealing
with.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because
The most likely cause for this is that you have packets outbound on port
5353 firewalled either locally or on your network device. When another
host pings the address, the responses are sent via multicast and Avahi
caches that response, and so can then use it without having to transmit
a packet.
This is a bug in CUPS ultimately, it's driving Avahi using the D-BUS API
(as opposed to manual service files in /etc/avahi/services, this is only
really used for a sysadmin to manually add services, most other types of
advertisements such as printers are expected to use the API to advertise
it).
Can someone experiencing this bug please report it to the PulseAudio
developers?
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/new
and then tell us the new bug ID.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Launchpad has imported 26 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=758772.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
If the problem is corrected as stated by Mauricio Grueso (Above) Why has
this not been fixed? His note was dated June of LAST YEAR! This fix
might also fix the MANY other bugs of the same type I have encountered.
I am no programmer so I really don't know how to incorporate Grueso's
fix. Thank you,
xchat is back, and Gianfranco wants to keep it.
Also, I see little value in a transitional package or similar when they
can't be upgraded from one to the other seamlessly. I'm therefore
closing both tasks.
** Changed in: hexchat (Ubuntu)
Status: New => Invalid
** Changed in: xchat
I'm running umask 027 (set in `.bashrc` for my user, which is copied to
my root session after using `su`) and can report this issue still occurs
for unprivileged containers under Debian 9 (stretch, stable) using LXC
2.0.7-2+deb9u2 and kernel 4.19.0-0.bpo.4-amd64. I can also confirm umask
at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Public bug reported:
Hi,
I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in keyboard
emulation mode) with a USB bluetooth dongle in an 18.04 machine, which
used to work some months ago.
Now I can still pair them, the ubuntu machine sees the devices and lists
as paired, but can't
Public bug reported:
Hi,
I'm currently trying to debug why my Bluetooth Barcode scanner
(emulating a keyboard) with a USB bluetooth dongle does not work anymore
with my 18.04, can't connect it anoymore (it used to work at lease
occasionally months ago.) It pairs, but can't be connected as a HID.
This bug was fixed in the package poppler - 0.76.1-0ubuntu3
---
poppler (0.76.1-0ubuntu3) eoan; urgency=medium
* d/p/glyphless-font.patch: Support Tesseract's glyphless font (LP:
#1830473)
-- Julian Andres Klode Sat, 25 May 2019 12:31:14
+0200
** Changed in: poppler (Ubuntu)
Public bug reported:
On my local network I find that with 18.04 network name lookups using
.local domains no not work unless stimulated by a non-18.04 machine
first. This is observed for ssh, http, https and ping, but probably not
limited to those.
To demonstrate this here is a ping example.
~
~ $ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1830531
Title:
.local domain look ups do not
Public bug reported:
There is 1 error.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: apparmor 2.12-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
apparmor:amd64: Install
NULL:
46 matches
Mail list logo
