You certainly seem to have the latest and greatest Intel GPU which
should support 4K up to 120Hz:
https://ark.intel.com/content/www/us/en/ark/products/196597/intel-
core-i7-1065g7-processor-8m-cache-up-to-3-90-ghz.html
So I suspect using "adapters" is the main issue. If you can then please
try
Ubuntu 19.10 is reaching end-of-life within days from now:
https://wiki.ubuntu.com/Releases
Please reproduce the bug on either 18.04 or 20.04 and then report a new
bug from that machine by running:
ubuntu-bug bluez
** Changed in: bluez (Ubuntu)
Status: New => Won't Fix
--
You
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Problems with locking the screen (and gnome-shell then crashing) lately
have mostly been bug 184, which you don't seem to have the fix
for... To get the fix please try:
sudo apt update
sudo apt full-upgrade
Reboot
and then verify your gnome-shell package is at least version 3.36.3.
**
** Summary changed:
- Will not logout or shutdown form guest-session
+ Will not logout or shutdown from guest-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1855350
Sigh indeed. The ignoring of this bug report (and many other bad, bad
decisions for that matter) has now lead us to just abandon Ubuntu
entirely. Even for non-server desktop use cases. I have no idea if the
original reported issue has ever actually been dealt with, and I guess I
never will.
--
@Yakir,
the dmesg in the #1 is not a complete one, could you please upload a new
one (remove the "snd-intel-dspcfg.dsp_driver=1").
BTW, could you please try the kernel older than 5.4.0-40.44-generic like
5.4.0-39/38/37/...
--
You received this bug notification because you are a member of
Hello Yancy, or anyone else affected,
Accepted quassel into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/quassel/1:0.12.4-3ubuntu1.18.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Yancy, or anyone else affected,
Accepted quassel into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/quassel/1:0.13.1-3ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
I have some early dell 4k 60hz screens - the ones which report 2 panels
internally for DP 60Hz - horrid hack I know; I recently got a new XPS
laptop and put Ubuntu on it.
That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens
I bought two slightly different
Hello Gunnar, or anyone else affected,
Accepted ibus into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ibus/1.5.22-2ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mattias, or anyone else affected,
Accepted openldap into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.42
+dfsg-2ubuntu3.9 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Mattias, or anyone else affected,
Accepted openldap into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.45
+dfsg-1ubuntu1.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Mattias, or anyone else affected,
Accepted openldap into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openldap/2.4.48+dfsg-
1ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Mattias, or anyone else affected,
Accepted openldap into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openldap/2.4.49+dfsg-
2ubuntu1.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Ryan, or anyone else affected,
Accepted openldap into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.42
+dfsg-2ubuntu3.9 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ryan, or anyone else affected,
Accepted openldap into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openldap/2.4.48+dfsg-
1ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ryan, or anyone else affected,
Accepted openldap into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.45
+dfsg-1ubuntu1.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
This bug has persisted over several years, and several versions, and
after a lot of investigation I'm not really any closer on what's going
on.
I have two pretty old GA MA78gm S2H mainboards, configured slightly
different, and otherwise working properly. Both
The verification of the Stable Release Update for software-properties
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
This bug was fixed in the package software-properties - 0.98.9.1
---
software-properties (0.98.9.1) focal; urgency=medium
* cloudarchive: Enable support for the Victoria Ubuntu Cloud Archive on
20.04 (LP: #1882583).
-- Corey Bryant Mon, 08 Jun 2020 16:46:09
-0400
**
> I wonder if you see anything related to systemd-resolved with 'journalctl |
> grep audit | grep systemd'
No, not since March 30th.
> at the time of the boot failure.
No log files were written at that time (no log entries made it to disk before
the segfault).
--
You received this bug
** Changed in: coreutils (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1219529
Title:
df -x tmpfs fails to exclude
** Changed in: coreutils (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1756595
Title:
disk space info inadvertently provides all
** Changed in: coreutils (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1827159
Title:
check_all_disks includes squashfs
After the crash (hid hangs, could be a side effect) this is the dmesg.0
file still existing
john@hydra:~$ tail -100 /var/log/dmesg.0
[7.277226] kernel: nvidia-uvm: Loaded the UVM driver, major device number
237.
[7.498321] kernel: cfg80211: Loading compiled-in X.509 certificates for
This bug was fixed in the package glib2.0 - 2.64.3-1~ubuntu20.04.1
---
glib2.0 (2.64.3-1~ubuntu20.04.1) focal; urgency=medium
* No-change backport from unstable / groovy to focal (LP: #1883694)
* control, gbp.conf: Use the ubuntu/focal branch
glib2.0 (2.64.3-1) unstable;
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
There are several reports on the net talking about random disconnects
with Bluetooth dongles reporting as BCM20702A0 and BCM20702A1, that
might be important.
Win10 experience the same problems, but it seems like they are able to
recover.
It seems like my HK Onyx Studio 4 has the same problem,
> We are reffering to the local stub resolver
yes, i understand that, but i'm asking if you are talking about local
traffic TO the stub resolver, or traffic FROM the stub resolver to your
upstream nameserver.
If you have pcap showing the problem, please attach it.
If you're not sure what I'm
Public bug reported:
This bug has persisted over several years, and several versions, and
after a lot of investigation I'm not really any closer on what's going
on.
I have two pretty old GA MA78gm S2H mainboards, configured slightly
different, and otherwise working properly. Both of them have
** Package changed: ubuntu => pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1886696
Title:
[Vostro 5490, Realtek ALC3204, Speaker, Internal]
You have been subscribed to a public bug:
I have ubuntu Ubuntu 20.04 LTS installed, together with windows (dual boot) on
my laptop.
There is no sound at all, seems like Pulseaudio / Alsa dont recognize the sound
card:
$ pacmd list-cards
0 card(s) available.
dmesg shows errors of
Hi @gregrwm,
Thanks for reporting this bug/regression.
Patch just submitted upstream to fix it [1].
Let's see how it goes.
cheers,
Mauricio
[1] https://github.com/karelzak/util-linux/pull/1095
** Changed in: util-linux (Ubuntu)
Status: New => In Progress
** Changed in: util-linux
Thank you for the answer. We are reffering to the local stub resolver(
127.0.0.53 ). As a workaround we have created symbolic link:
sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
However, with the local stub resolver is still not working.
--
You received this bug notification
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.9
---
pulseaudio (1:11.1-1ubuntu7.9) bionic; urgency=medium
[Kai-Chuan Hsieh]
* alsa-mixer: Correct ucm card name (LP: #1881094)
[Hui Wang]
* d/p/0901-alsa-solaris-oss-remove-unnecessary-error-handling-w.patch
The verification of the Stable Release Update for pulseaudio has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for pulseaudio has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.9
---
pulseaudio (1:11.1-1ubuntu7.9) bionic; urgency=medium
[Kai-Chuan Hsieh]
* alsa-mixer: Correct ucm card name (LP: #1881094)
[Hui Wang]
* d/p/0901-alsa-solaris-oss-remove-unnecessary-error-handling-w.patch
Public bug reported:
Text alignment in updates tab is not consistent with other tabs. Text is
center aligned as shown in screenshot. I think it should be left
aligned.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.98.9
ProcVersionSignature: Ubuntu
** Description changed:
+ [impact]
+
+ assertion failure in systemd-journal-remote
+
+ [test case]
+
+ only happens under specific circumstances, which is unclear exactly how
+ to reproduce it
+
+ [regression potential]
+
+ any regression would likely result in the failure/crash of systemd-
Public bug reported:
Reproducible on my system. Whenever my computer "sleeps" while running a
specific program (Phenix), when I return to check on the job, the
Desktop screen does not load. Alt-F2 and other routes have not been
successful in recovery the Desktop GUI or log-in. However, if I stay
as Eoan will be EOL in weeks, marking this wontfix.
** Changed in: systemd (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
- After applying updates to Ubuntu 18.04 my desktop (apple mini with
+ [impact]
+
+ systemd sometimes crashes on boot due to free of uninitalized var
+
+ [test case]
+
+ a specific system setup is required, see original description
+
+ [regression potential]
+
+ any
All autopkgtests for the newly accepted apt (2.0.3) for focal have finished
running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.11-0ubuntu27 (amd64)
reprotest/0.7.14 (amd64)
Please visit the excuses page listed below and investigate the
All autopkgtests for the newly accepted less (551-1ubuntu0.1) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
mercurial/5.3.1-1ubuntu1 (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding
** Information type changed from Public to Public Security
** Information type changed from Public Security to Private
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
All autopkgtests for the newly accepted xz-utils (5.2.4-1ubuntu1) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
epson-inkjet-printer-escpr/1.7.7-1 (arm64)
apt/2.0.2 (armhf)
ostree/2020.3-1 (ppc64el)
firejail/0.9.62-3 (ppc64el)
** Changed in: libimobiledevice (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1721398
Title:
Missing "idevicerestore" &
** Description changed:
+ [impact]
+
+ shutdown sometimes fails to unmount some fs, which causes shutdown hang
+
+ [test case]
+
+ it's unclear what the specific configuration is to be able to reproduce
+ this, but there are some examples in the upstream bug
+
+ [regression potential]
+
+ as
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: libseccomp (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Bug watch added: Debian Bug tracker #963042
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963042
** Also affects: libimobiledevice (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963042
Importance: Unknown
Status: Unknown
--
You received this bug
Jul 07 00:08:37 betty io.elementary.a[3348]: gtk_widget_size_allocate():
attempt to allocate widget with width -5 and height 17
Jul 07 00:08:40 betty io.elementary.a[3348]: gtk_widget_size_allocate():
attempt to allocate widget with width -5 and height 17
Jul 07 00:08:41 betty gnome-shell[1966]:
Public bug reported:
New bug for me. Issue was fine till last week. I think this may be
related to the following as it started happening shortly thereafter.
I have XPS13 with second monitor, all working fine till I lock screen or
suspend. Then my second monitor will not 'resume'. I.e. stays off.
*** This bug is a duplicate of bug 1833671 ***
https://bugs.launchpad.net/bugs/1833671
** This bug has been marked a duplicate of bug 1833671
bond interfaces stop working after restart of systemd-networkd
--
You received this bug notification because you are a member of Ubuntu
Touch
This seems related:
* https://bugzilla.redhat.com/show_bug.cgi?id=1653068
* https://github.com/systemd/systemd/pull/11157
I can't say why the libseccomp update would change anything, though the
redhat bug shows an AVC denial, so I wonder if you see anything related
to systemd-resolved with
Note that 2.4.1-0ubuntu0.18.04.2 was previously in bionic and had been
since May of 2019 (2.3.1-2.1ubuntu4 is what bionic was released with,
but later updated to 2.4.1-0ubuntu0.18.04.2). 2.4.1-0ubuntu0.18.04.2 can
be found here:
@Erik, thanks for confirming it's fixed for you on focal. We should get
the poppler version in the evince snap updated
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1885313
Are you referring to edns0 from glibc to the local stub resolver, or
edns0 from systemd-resolved to the upstream nameserver?
I don't see any problem when i resolve the name on bionic:
$ lsb_release -c
Codename: bionic
$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.41
@Seb, Ok, got it, this bug needs both kernel fix and pulseaudio fix, SRU
the kernel fix first, then the fix of pulseaudio.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
We discussed it in our meeting, it probably makes sense to include it in
the next SRU we do but we don't believe it deserves rls tracking,
updating the tag according to that decision
** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing
--
You received this bug notification because
@Hui, since there is a pulseaudio targetted entry there I'm assigning
that to you, feel free to close as invalid if only the kernel needs
fixing
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Hui Wang (hui.wang)
** Changed in: pulseaudio (Ubuntu Bionic)
Assignee:
** Package changed: apt (Ubuntu) => command-not-found (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1886618
Title:
command-not-found gets stuck on locales with
@r-2ohn-d can you test with systemd from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
--
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/1881972
Title:
Thank you for your bug report, what Ubuntu version and locale do you
use? It's a bit weird, it was just broken on some locales there would be
other reports about the issue...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Low
--
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/1753115
Title:
add-apt-repository
Public bug reported:
The printer always goes to stopped state in Ubuntu 20.04. Print
properties window has status message saying: "cups-pki-expired". I have
HP color laserjet m552, which Ubuntu discovers directly from the local
network and configures automatically.
ProblemType: Bug
add-apt-repository -h mentions the option, though.
** Tags added: focal
--
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/1753115
Title:
add-apt-repository
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/386957
--
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/1838329
Sorry, bug fixed after Sys update (facepalm)
On Tue, Jul 7, 2020 at 5:24 PM Jeremielapuree <260...@bugs.launchpad.net>
wrote:
> Does the bug still occur with wine-5.12?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (283421).
>
Public bug reported:
* Impact
That's the current GNOME stable update, including some fixes and translation
updates
https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS
* Test case
The update is part of GNOME stable updates
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1881094
Title:
Support kernel 5.4 Intel sound driver on bionic
Status in OEM Priority
My Problem was just a naming issue :-
$ dmesg | grep -i 'bluetooth'
if you are facing some naming problem,the output of above command should
be somthing like this ->
Bluetooth hci0: Direct firmware load for brcm/BCM43142A0-0489-e062.hcd failed
with error -2
Bluetooth: hci0: BCM: Patch
** Package changed: ubuntu => alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1886626
Title:
after login to gnome with snd_hda_intel :00:1f.3:
You have been subscribed to a public bug:
After login to gnome, login takes an unsual amount of time.
Goes back to login screen.
On second login, works normally but audio sliders are not showing correctly.
After a while, it operates normally.
Logs are showing a lot of
snd_hda_intel :00:1f.3:
Jul 07 00:08:37 betty io.elementary.a[3348]: gtk_widget_size_allocate():
attempt to allocate widget with width -5 and height 17
Jul 07 00:08:40 betty io.elementary.a[3348]: gtk_widget_size_allocate():
attempt to allocate widget with width -5 and height 17
Jul 07 00:08:41 betty gnome-shell[1966]:
Does the bug still occur with wine-5.12?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-good0.10 in
Ubuntu.
https://bugs.launchpad.net/bugs/260918
Title:
needed: libv4l and associated application patches (or
I redeployed the system where this failures was original observed and recreated
the issue.
Running 'sudo vgck --updatemetadata s5lp8-vg' did work around this bug, when
run after the upgrade but prior to the reboot.
Here is the vgdisplay output requested by Steve:
ubuntu@s5lp8:~$ sudo vgdisplay
** Description changed:
The bug in question: https://askubuntu.com/q/1142923/162831
- Namely, cnf-update-db takes forever if your locale has different collation
rules from English such as different sorting and/or case conversion.
+ Namely, cnf-update-db takes forever and eats almost all your
Confirmed by me.
** Description changed:
The bug in question: https://askubuntu.com/q/1142923/162831
- Namely, cnf-update-db takes forever if your locale has a different collation
rules from English such as different sorting and/or case conversion.
+ Namely, cnf-update-db takes forever if
Public bug reported:
The bug in question: https://askubuntu.com/q/1142923/162831
Namely, cnf-update-db takes forever if your locale has different collation
rules from English such as different sorting and/or case conversion.
A workaround by supplying a C locale:
82 matches
Mail list logo
