ubuntu@lp1849733-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.33 amd64system and service manager
ubuntu@lp1849733-b:~$ dig +noanswer +noedns toomany.ddstreet.org
;; Truncated, retrying in TCP mode.
; <<>> DiG 9.11.3-1ubuntu1.10-Ubuntu <<>> +noanswer +noedns
ubuntu@lp1849733-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
ubuntu@lp1849733-b:~$ telnet toomany100.ddstreet.org
telnet: could not resolve toomany100.ddstreet.org/telnet: Temporary failure in
name resolution
ubuntu@lp1849733-b:~$
ubuntu@lp1832672-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
ubuntu@lp1832672-b:~$ grep bar /etc/hosts
127.0.2.1 foo # bar
ubuntu@lp1832672-b:~$ systemd-resolve -4 bar
bar: 127.0.2.1
-- Information acquired via protocol DNS in 1.9ms.
--
[Expired for tzdata (Ubuntu) because there has been no activity for 60
days.]
** Changed in: tzdata (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
It seems to be a problem from the chip series itself since in 16.04.03
it also does not get detected. Or the internal mic is flawed, I still
need to test in windows 10 to be sure if it is a alsa driver problem to
this chip or a hardware problem
--
You received this bug notification because you
Public bug reported:
I am using two monitors, they both are displaying the same image. In
settings, only one monitor is recognized (technically they have the same
name, though). I have tried to go into arandr to see what I could do but
only one monitor is recognized there.
ProblemType: Bug
indeed, the headphone mic is working perfectly, so it`s not detecting
the internal, i am still to test the internal mic in others SOs to
attest that is an alsa-driver bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I should have mentioned that I have a fix for this too just running it
by mvo.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852773
Title:
test failures on
I should have mentioned that I have a fix for this just running it by
mvo.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval
Target machins is Ubuntu 16.04:
Linux scadauser-NP3020M3 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri
Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
This problem also affected me after a new qt installation ( I only
copied the lib, plugins, qml into target machine's /usr/local/qt5.7 ).
Same issue on Lenovo Yoga C940, Ubuntu 19.10, kernel 5.3.0-23-generic
x86_64. Mic not working, audio not working properly with missing
speakers.
Alsa info -> http://alsa-
project.org/db/?f=863a8059dba17f148fb2d3b5b1705d29bc900218
--
You received this bug notification because you are a member of
attaching journalctl.log
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853199/+attachment/5306520/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
It happened around this time (journalctl.log):
Nov 19 20:38:00 tv xdg-desktop-por[3284]: xdg-desktop-portal-gtk: Fatal IO
error 11 (Resource temporarily unavailable) on X server :0.
Nov 19 20:38:00 tv gdm-password][1338]: pam_unix(gdm-password:session): session
closed for user tv
Nov 19
Public bug reported:
A bit similar to "30 seconds boot delay when root fs is on lvm":
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1807499
I installed Kubuntu 19.04 with 2 LVM volume groups (one per disk). My root and
my /usr are both located on the same LVM. Mounting /usr takes 30s,
** Summary changed:
- Susystemd-analyze blame returns "Bootup is not yet finished"
+ Systemd-analyze blame returns "Bootup is not yet finished"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thanks, reassigning
** Package changed: glib2.0 (Ubuntu) => udisks2 (Ubuntu)
** Also affects: udisks via
https://github.com/storaged-project/udisks/issues/709
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
Copy text anwyhere (browser, terminal) crashes user session and shows login
screen.
It takes few login attempts to actually login back.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname:
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval fails on focal
Status in
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852773
Title:
test failures on focal due to missing build-depends on gpg and
All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.10) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.9-0ubuntu7.10 (amd64, i386)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted apport (2.20.10-0ubuntu27.4) for disco
have finished running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.10-0ubuntu27.4 (amd64, i386)
Please visit the excuses page listed below and investigate the
This is actually being tracked in bug 1835738.
** Changed in: python3-defaults (Ubuntu Bionic)
Status: New => In Progress
** Changed in: python3-defaults (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: python3-defaults (Ubuntu Bionic)
Importance: Undecided
Update: the issue at GNOME repository was closed (
https://gitlab.gnome.org/GNOME/glib/issues/1942#note_651026 ), and a new
issue was filed for the `udisks` repository: https://github.com
/storaged-project/udisks/issues/709 , with probable bug location at or
near https://github.com/storaged-
All autopkgtests for the newly accepted apport (2.20.11-0ubuntu8.3) for eoan
have finished running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.11-0ubuntu8.3 (amd64)
Please visit the excuses page listed below and investigate the failures,
I am having the same problem with a new dell-g3-3590,
arecord -l gives:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3254 Analog [ALC3254 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 2: ALC3254 Alt Analog
if you can recompile a kernel, using Mark Brown's for-next should have
have all the latest changes from Google for Cyan.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
In downstream bug report http://pad.lv/1609750 it was noted that this
patch would be needed:
https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f
However I've tested 5.4rc7 and it does not seem to help. Do people know
of other non-upstreamed patches required for the
Hello dann, or anyone else affected,
Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.10 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello dann, or anyone else affected,
Accepted apport into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.10-0ubuntu27.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello dann, or anyone else affected,
Accepted apport into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu8.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1848587
Title:
lxc 3.0.4-0ubuntu1 ADT test failure with
Flagging this as wont fix as heartbeat is already being kept just for
historical reasons (and systemd-networkd can workaround that by the fix
we're backporting to it: KeepConfiguration .service file stanza).
** Changed in: heartbeat (Ubuntu Eoan)
Assignee: Rafael David Tinoco (rafaeldtinoco)
(k)rafaeldtinoco@kcluster01:~$ dpkg -l | grep "ii systemd "
ii systemd243-3ubuntu1amd64system and service manager
k)rafaeldtinoco@kcluster01:~$ for name in kcluster01 kcluster02
kcluster03; do ssh $name "dpkg -l | grep systemd "; done | grep "ii
systemd "
ii systemd
The attachment "Check for active service, not existence of binary."
seems to be a patch. If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
Status in systemd
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
sdezial notes this being terser. I do the long form out of superstitious awe
at the notion of a return code of zero being "true", even though it always
is, but this would be terser and also correct:
if systemctl is-active systemd-resolved > /dev/null 2>&1; then
--
You received this bug
I have the same issue as echaskaris above. Audio plays, but volume
control in the top right corner, as well as with keyboard keys defaults
to the HDMI output, so there's no control. Setting it to line out
restores volume control there for the duration of my session.
--
You received this bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
Status in systemd package in Ubuntu:
New
Bug
Public bug reported:
The functionality exists to allow users to revert to the traditional ifupdown
package for network configuration. Alongside this, systemd's often-buggy
resolver can be disabled. However, there's a logic error in the systemd-
supplied /etc/dhcp/dhclient-enter-hooks.d/resolved
I don't think it's quite the same issue as 833 upstream, though the
symptoms are similar.
I disabled GLX and it didn't change any symptoms, which I think it would
if it were the same as 833 (?).
I did see a similar issue reported on Arch where the symptoms only
occurred when a USB C monitor was
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853120/+attachment/5306476/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Launchpad has imported 13 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=93610.
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
Could you check if upstream
https://gitlab.freedesktop.org/xorg/xserver/issues/833 matches yours?
Does is get triggered by using some specific software?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Thank you for your bug report. Could you add the gdb backtrace to the
report?
** Changed in: xorg (Ubuntu)
Importance: Undecided => High
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #833
For me, HDMI audio is selected in the options but sound plays in the
desired device. What is annoying is that I have to go to settings every
time I need to adjust the volume because the top right menu adjusts HDMI
audio. Am I having the same issue?
--
You received this bug notification because
I would like to add that I also experience the behaviour reported in
posts #16
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570/comments/16)
and #19
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570/comments/19).
--
You received this bug notification because
Public bug reported:
I'm using a Dell XPS 9380 ("developer edition") connected to an external
monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor with
no issues. On upgrading to 19.10 xorg crashes with a bus error within a
few seconds or minutes of using the
Thanks for the investigation, looks like it's a vim issue from your
bisecting
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gvfs (Ubuntu)
Status: New => Invalid
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Low
--
You received this bug
Public bug reported:
Allowed users and groups as admins for pkexec are defined in:
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
[Configuration]
AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin
As you can see, I added unix-group:localadmin
My user is
I've updated my cyan (Acer Chromebook R11) to kernel 5.4rc7 from
Ubuntu's mainline PPA, but the audio is still not working (no audio
device visible according to pulseaudio).
Are you aware of something else that still needs upstreaming beside the
mentioned
54 matches
Mail list logo
